This is a comment left during a code review.
Path: apps/code/src/renderer/features/billing/hooks/useUsageLimitDetection.ts
Line: 22-32

Comment:
**Idle usage-exceeded state silently dropped**

The previous code showed a modal for both active and idle states when usage was exceeded. After this change, if usage is exceeded while no session has `isPromptPending`, `hasAlertedRef.current` is never set to `true`, so the condition re-evaluates on every usage poll (now every 30 s) but never triggers anything. Users who hit their limit while idle receive no proactive notification — they'll only see the modal if they subsequently start a prompt that bounces back a 429 and gets caught in `service.ts`.

If this is intentional (prefer reactive detection over proactive polling for the idle case), a comment here would help future maintainers understand why the `show("idle")` path was removed entirely.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: apps/code/src/shared/errors.ts
Line: 23-27

Comment:
**Bare `"429"` substring pattern is overly broad**

`includesAny` does a case-insensitive `.includes()` check, so any error message containing the three characters `429` (e.g., `"session not found after 429 retries"`, a port number, a token ID, etc.) will be classified as a rate-limit error and suppress fatal-error recovery in `isFatalSessionError`. Prefer matching on the full HTTP status line or a more anchored pattern like `" 429 "` / `"status 429"` to reduce the risk of false positives.

How can I resolve this? If you propose a fix, please make it concise.